SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

</head>

</h1>

</header>

<p><b>Reference Model of Open Distributed Processing</b> (<b>RM-ODP</b>) is a <a href="Reference_model" title="Reference model">reference model</a> in <a href="Computer_science" title="Computer science">computer science</a>, which provides a co-ordinating framework for the standardization of <a href="Open_system_(computing)" title="Open system (computing)">open</a> <a href="Distributed_systems" class="mw-redirect" title="Distributed systems">distributed</a> processing (ODP). It supports <a href="Distributed_systems" class="mw-redirect" title="Distributed systems">distribution</a>, <a href="Interoperability" title="Interoperability">interworking</a>, <a href="Platform_(computing)" class="mw-redirect" title="Platform (computing)">platform</a> and technology independence, and <a href="Porting" title="Porting">portability</a>, together with an <a href="Enterprise_architecture_framework" title="Enterprise architecture framework">enterprise architecture framework</a> for the <a href="Specification" class="mw-redirect" title="Specification">specification</a> of ODP systems.

</p><p>RM-ODP, also named <i>ITU-T Rec. X.901-X.904</i> and <i>ISO/IEC 10746</i>, is a joint effort by the <a href="International_Organization_for_Standardization" title="International Organization for Standardization">International Organization for Standardization</a> (ISO), the <a href="International_Electrotechnical_Commission" title="International Electrotechnical Commission">International Electrotechnical Commission</a> (IEC) and the <a href="ITU-T" title="ITU-T">Telecommunication Standardization Sector</a> (ITU-T).<sup id="cite_ref-1" class="reference"><a href="#cite_note-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading2"><h2 id="Overview">Overview</h2></div>

<p>The RM-ODP is a <a href="Reference_model" title="Reference model">reference model</a> based on precise concepts derived from current distributed processing developments and, as far as possible, on the use of <a href="Formal_methods" title="Formal methods">formal description techniques</a> for specification of the <a href="Enterprise_architecture" title="Enterprise architecture">architecture</a>. Many RM-ODP concepts, possibly under different names, have been around for a long time and have been rigorously described and explained in exact philosophy (for example, in the works of <a href="Mario_Bunge" title="Mario Bunge">Mario Bunge</a>) and in <a href="Systems_thinking" title="Systems thinking">systems thinking</a> (for example, in the works of <a href="Friedrich_Hayek" title="Friedrich Hayek">Friedrich Hayek</a>). Some of these concepts—such as <a href="Abstraction" title="Abstraction">abstraction</a>, composition, and <a href="Emergence" title="Emergence">emergence</a>—have recently been provided with a solid mathematical foundation in <a href="Category_theory" title="Category theory">category theory</a>.

</p><p>RM-ODP has four fundamental elements:

</p>

<ul><li>an <a href="Object-oriented_analysis_and_design" title="Object-oriented analysis and design">object modelling approach</a> to system specification;</li>

<li>the specification of a system in terms of separate but interrelated viewpoint specifications;</li>

<li>the definition of a system infrastructure providing <a href="Transparency_(human%E2%80%93computer_interaction)" title="Transparency (human–computer interaction)">distribution transparencies</a> for system applications; and</li>

<li>a framework for assessing <a href="Conformance_testing" title="Conformance testing">system conformance</a>.</li></ul>

<p>The RM-ODP family of recommendations and international standards defines a system of interrelated essential concepts necessary to specify <a href="Open_system_(computing)" title="Open system (computing)">open</a> <a href="Distributed_systems" class="mw-redirect" title="Distributed systems">distributed</a> processing systems and provides a well-developed enterprise architecture framework for structuring the specifications for any large-scale systems including software systems.

</p>

<div class="mw-heading mw-heading2"><h2 id="History">History</h2></div>

<p>Much of the preparatory work that led into the adoption of RM-ODP as an ISO standard was carried out by the <a href="Advanced_Networked_Systems_Architecture" class="mw-redirect" title="Advanced Networked Systems Architecture">Advanced Networked Systems Architecture</a> (ANSA) project. This ran from 1984 until 1998 under the leadership of <a href="Andrew_Herbert" title="Andrew Herbert">Andrew Herbert</a> (now MD of Microsoft Research in Cambridge), and involved a number of major computing and telecommunication companies. Parts 2 and 3 of the RM-ODP were eventually adopted as <a href="ISO_standard" class="mw-redirect" title="ISO standard">ISO standards</a> in 1996. Parts 1 and 4 were adopted in 1998.

</p>

<div class="mw-heading mw-heading2"><h2 id="RM-ODP_topics">RM-ODP topics</h2></div>

<div class="mw-heading mw-heading3"><h3 id="RM-ODP_standards">RM-ODP standards</h3></div>

<p>RM-ODP consists of four basic <a href="ITU-T#Series_and_Recommendations" title="ITU-T">ITU-T Recommendations</a> and

<a href="List_of_ISO_standards" title="List of ISO standards">ISO/IEC International Standards</a>:<sup id="cite_ref-2" class="reference"><a href="#cite_note-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-3" class="reference"><a href="#cite_note-3"><span class="cite-bracket">[</span>3<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-4" class="reference"><a href="#cite_note-4"><span class="cite-bracket">[</span>4<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-5" class="reference"><a href="#cite_note-5"><span class="cite-bracket">[</span>5<span class="cite-bracket">]</span></a></sup>

</p>

<ol><li>Overview:<sup id="cite_ref-6" class="reference"><a href="#cite_note-6"><span class="cite-bracket">[</span>6<span class="cite-bracket">]</span></a></sup> Contains a motivational overview of ODP, giving scoping, justification and explanation of key concepts, and an outline of the ODP architecture. It contains explanatory material on how the RM-ODP is to be interpreted and applied by its users, who may include standard writers and architects of ODP systems.</li>

<li>Foundations:<sup id="cite_ref-7" class="reference"><a href="#cite_note-7"><span class="cite-bracket">[</span>7<span class="cite-bracket">]</span></a></sup> Contains the definition of the concepts and analytical framework for normalized description of (arbitrary) distributed processing systems. It introduces the principles of conformance to ODP standards and the way in which they are applied. In only 18 pages, this standard sets the basics of the whole model in a clear, precise and concise way.</li>

<li>Architecture:<sup id="cite_ref-8" class="reference"><a href="#cite_note-8"><span class="cite-bracket">[</span>8<span class="cite-bracket">]</span></a></sup> Contains the specification of the required characteristics that qualify distributed processing as open. These are the constraints to which ODP standards must conform. This recommendation also defines RM-ODP viewpoints, subdivisions of the specification of a whole system, established to bring together those particular pieces of information relevant to some particular area of concern.</li>

<li>Architectural Semantics:<sup id="cite_ref-9" class="reference"><a href="#cite_note-9"><span class="cite-bracket">[</span>9<span class="cite-bracket">]</span></a></sup> Contains a formalization of the ODP modeling concepts by interpreting many concepts in terms of the constructs of the different standardized formal description techniques.</li></ol>

<div class="mw-heading mw-heading3"><h3 id="Viewpoints_modeling_and_the_RM-ODP_framework">Viewpoints modeling and the RM-ODP framework</h3></div>

<p>Most complex system specifications are so extensive that no single individual can fully comprehend all aspects of the specifications. Furthermore, we all have different interests in a given system and different reasons for examining the system's specifications. A business executive will ask different questions of a system make-up than would a system implementer. The concept of RM-ODP viewpoints framework, therefore, is to provide separate viewpoints into the specification of a given complex system. These viewpoints each satisfy an audience with interest in a particular set of aspects of the system. Associated with each viewpoint is a viewpoint language that optimizes the vocabulary and presentation for the audience of that viewpoint.

</p><p><a href="Viewpoint_modeling" class="mw-redirect" title="Viewpoint modeling">Viewpoint modeling</a> has become an effective approach for dealing with the inherent complexity of large distributed systems. Current software architectural practices, as described in <a href="IEEE_1471" title="IEEE 1471">IEEE 1471</a>, divide the design activity into several areas of concerns, each one focusing on a specific aspect of the system. Examples include the <a href="4%2B1" class="mw-redirect" title="4+1">"4+1" view model</a>, the <a href="Zachman_Framework" title="Zachman Framework">Zachman Framework</a>, <a href="TOGAF" class="mw-redirect" title="TOGAF">TOGAF</a>, <a href="DoDAF" class="mw-redirect" title="DoDAF">DoDAF</a> and, of course, RM-ODP.

</p><p>A <a href="Viewpoint_model" class="mw-redirect" title="Viewpoint model">viewpoint</a> is a subdivision of the specification of a complete system, established to bring together those particular pieces of information relevant to some particular area of concern during the analysis or design of the system. Although separately specified, the viewpoints are not completely independent; key items in each are identified as related to items in the other viewpoints. Moreover, each viewpoint substantially uses the same foundational concepts (defined in Part 2 of RM-ODP). However, the viewpoints are sufficiently independent to simplify reasoning about the complete specification. The mutual consistency among the viewpoints is ensured by the architecture defined by RM-ODP, and the use of a common object model provides the glue that binds them all

together.

</p><p>More specifically, the RM-ODP framework provides five generic and complementary viewpoints on the system and its environment:

</p>

<ul><li>The <i>enterprise viewpoint</i>, which focuses on the purpose, scope and policies for the system. It describes the business requirements and how to meet them.</li>

<li>The <i>information viewpoint</i>, which focuses on the semantics of the information and the information processing performed. It describes the information managed by the system and the structure and content type of the supporting data.</li>

<li>The <i>computational viewpoint</i>, which enables distribution through functional decomposition on the system into objects which interact at interfaces. It describes the functionality provided by the system and its functional decomposition.</li>

<li>The <i>engineering viewpoint</i>, which focuses on the mechanisms and functions required to support distributed interactions between objects in the system. It describes the distribution of processing performed by the system to manage the information and provide the functionality.</li>

<li>The <i>technology viewpoint</i>, which focuses on the choice of technology of the system. It describes the technologies chosen to provide the processing, functionality and presentation of information.</li></ul>

<p>Currently there is growing interest in the use of <a href="Unified_Modeling_Language" title="Unified Modeling Language">UML</a> for system modelling. However,

there is no widely agreed approach to the structuring of such specifications. This adds to the cost of adopting the use of <a href="Unified_Modeling_Language" title="Unified Modeling Language">UML</a> for system specification, hampers communication between system developers and makes it difficult to relate or merge system specifications where there is a need to integrate IT systems.

</p><p>Although the ODP reference model provides abstract languages for the relevant concepts, it does not prescribe particular notations to be used in the individual viewpoints. The viewpoint languages defined in the reference model are abstract languages in the sense that they define what concepts should be used, not how they should be

represented. This lack of precise notations for expressing the different models involved in a multi-viewpoint specification of a system is a common feature for most <a href="Enterprise_architecture_framework" title="Enterprise architecture framework">enterprise architectural approaches</a>, including the <a href="Zachman_Framework" title="Zachman Framework">Zachman Framework</a>, the "<a href="4%2B1" class="mw-redirect" title="4+1">4+1</a>" model, or the RM-ODP. These approaches were consciously defined in a notation- and representation-neutral manner to increase their use and flexibility. However, this makes more difficult, among other things, the development of industrial tools for modeling the viewpoint specifications, the formal analysis of the specifications produced, and the possible derivation of implementations from the system specifications.

</p><p>In order to address these issues, ISO/IEC and the ITU-T started a joint project in 2004: "ITU-T Rec. X.906|ISO/IEC 19793: Information technology - Open distributed processing - Use of UML for ODP system specifications". This document (usually referred to as <a rel="nofollow" class="external text" href="http://www.lcc.uma.es/~av/download/UML4ODP_IS_V2.pdf">UML4ODP</a>) defines use of the <a href="Unified_Modeling_Language" title="Unified Modeling Language">Unified Modeling Language</a> 2 (UML 2; ISO/IEC 19505), for expressing the specifications of open distributed systems in terms of the viewpoint specifications defined by the RM-ODP.

</p><p>It defines a set of <a href="Profile_(UML)" title="Profile (UML)">UML Profiles</a>, one for each viewpoint language and one to express the correspondences between viewpoints, and an approach for structuring them according to the RM-ODP principles. The purpose of "UML4ODP" to allow ODP modelers to use the UML notation for expressing their ODP specifications in a standard graphical way; to allow UML modelers to use the RM-ODP concepts and mechanisms to structure their large UML system specifications according to a mature and standard proposal; and to allow UML tools to be used to process viewpoint specifications, thus facilitating the software design process and the <a href="Enterprise_architecture" title="Enterprise architecture">enterprise architecture</a> specification of large software systems.

</p><p>In addition, ITU-T Rec. X.906 | ISO/IEC 19793 enables the seamless integration of the RM-ODP <a href="Enterprise_architecture_framework" title="Enterprise architecture framework">enterprise architecture framework</a> with the <a href="Model-driven_architecture" title="Model-driven architecture">Model-Driven Architecture (MDA)</a> initiative from the OMG, and with the <a href="Service-oriented_architecture" title="Service-oriented architecture">service-oriented architecture</a> (SOA).

</p>

<div class="mw-heading mw-heading2"><h2 id="Applications">Applications</h2></div>

<p>In addition, there are several projects that have used or currently use RM-ODP for effectively structuring their systems specifications:

</p>

<ul><li>The COMBINE project<sup id="cite_ref-10" class="reference"><a href="#cite_note-10"><span class="cite-bracket">[</span>10<span class="cite-bracket">]</span></a></sup></li>

<li>The ENVRI and ENVRIplus projects for common operations of environmental research infrastructures are developing the ENVRI Reference Model<sup id="cite_ref-11" class="reference"><a href="#cite_note-11"><span class="cite-bracket">[</span>11<span class="cite-bracket">]</span></a></sup></li>

<li>The Reference Architecture for Space Data Systems (RASDS)<sup id="cite_ref-12" class="reference"><a href="#cite_note-12"><span class="cite-bracket">[</span>12<span class="cite-bracket">]</span></a></sup> From the Consultative Committee for Space Data Systems.</li>

<li>Interoperability Technology Association for Information Processing (INTAP), Japan.<sup id="cite_ref-13" class="reference"><a href="#cite_note-13"><span class="cite-bracket">[</span>13<span class="cite-bracket">]</span></a></sup></li>

<li>The European Advanced Informatics in Medicine (AIM) OpenLabs project.<sup id="cite_ref-14" class="reference"><a href="#cite_note-14"><span class="cite-bracket">[</span>14<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-15" class="reference"><a href="#cite_note-15"><span class="cite-bracket">[</span>15<span class="cite-bracket">]</span></a></sup></li>

<li>The Synapses European project.<sup id="cite_ref-16" class="reference"><a href="#cite_note-16"><span class="cite-bracket">[</span>16<span class="cite-bracket">]</span></a></sup></li></ul>

<p>A 239-item reference list covering RM-ODP standards as well as related research, applications and case studies was included in.<sup id="cite_ref-17" class="reference"><a href="#cite_note-17"><span class="cite-bracket">[</span>17<span class="cite-bracket">]</span></a></sup>

</p>

<ul><li><a href="Enterprise_Architecture_framework" class="mw-redirect" title="Enterprise Architecture framework">Enterprise Architecture framework</a></li>

<li><a href="Enterprise_Collaboration_Architecture" title="Enterprise Collaboration Architecture">Enterprise Collaboration Architecture</a></li>

<li><a href="Enterprise_Modelling_Methodology/Open_Distributed_Processing" class="mw-redirect" title="Enterprise Modelling Methodology/Open Distributed Processing">Enterprise Modelling Methodology/Open Distributed Processing</a> (EMM/ODP)</li>

<li><a href="Reference_model" title="Reference model">Reference model</a></li>

<li><a href="Triune_Continuum_Paradigm" class="mw-redirect" title="Triune Continuum Paradigm">Triune Continuum Paradigm</a></li>

<li><a href="View_model" title="View model">View model</a></li>

<div class="mw-heading mw-heading2"><h2 id="Notes_and_references">Notes and references</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist">

<li id="cite_note-1"><span class="mw-cite-backlink"><b><a href="#cite_ref-1">^</a></b></span> <span class="reference-text">A complete and updated list of references to publications related to RM-ODP (books, journal articles, conference papers, etc.) is available at the <a rel="nofollow" class="external text" href="http://www.rm-odp.net/publications.html">RM-ODP resource site</a>.</span>

</li>

In the same series as the RM-ODP are a number of other standards and recommendations for the specification and development of open and distributed system, for which RM-ODP provides a standardization framework:

<ul><li>ITU-T Rec. X.950 | ISO/IEC 13235-1:1998, Trading function: Specification.</li>

<li>ITU-T Rec. X.952 | ISO/IEC 13235-3:1998, Provision of Trading Function using OSI directory service.</li>

<li>ITU-T Rec. X.920 | ISO/IEC 14750:1999, Interface Definition Language.</li>

<li>ITU-T Rec. X.931 | ISO/IEC 14752:2000, Protocol support for computational interactions.</li>

<li>ITU-T Rec. X.930 | ISO/IEC 14753:1999, Interface references and binding.</li>

<li>ITU-T Rec. X.960 | ISO/IEC 14769:2001, Type repository function.</li>

<li>ITU-T Rec. X.910 | ISO/IEC 14771:1999, Naming framework.</li>

<li>ITU-T Rec. X.911 | ISO/IEC 15414:2002, <a rel="nofollow" class="external text" href="http://www.joaquin.net/ODP/DIS_15414_X.911.pdf">Reference model - Enterprise language</a>.</li>

<li>ISO/IEC 19500-2:2003, General Inter-ORB Protocol (GIOP)/Internet Inter-ORB Protocol (IIOP).</li></ul>

</span></li>

<li id="cite_note-3"><span class="mw-cite-backlink"><b><a href="#cite_ref-3">^</a></b></span> <span class="reference-text">Copies of the RM-ODP family of standards can be obtained either from <a rel="nofollow" class="external text" href="http://www.iso.ch">ISO</a> or from <a rel="nofollow" class="external text" href="http://www.itu.int/">ITU-T</a>. Parts 1 to 4 of the RM-ODP are available for from <a rel="nofollow" class="external text" href="http://isotc.iso.ch/livelink/livelink/fetch/2000/2489/Ittf_Home/PubliclyAvailableStandards.htm">free download from ISO</a>. All ODP-related ITU-T Recommendations, including X.9xx series, are <a rel="nofollow" class="external text" href="http://www.itu.int/rec/T-REC-X/en">freely available from the ITU-T</a>.</span>

</li>

<li id="cite_note-4"><span class="mw-cite-backlink"><b><a href="#cite_ref-4">^</a></b></span> <span class="reference-text">There is also a very useful <a rel="nofollow" class="external text" href="http://www.joaquin.net/ODP">hyperlinked version</a> of Parts 2 and 3 of the RM-ODP, together with an index to the Reference Model, made available in keeping with a resolution of the ISO council. The Table of Contents and Index were prepared by Lovelace Computing and are being made available by Lovelace Computing as a service to the standards community.</span>

</li>

<li id="cite_note-5"><span class="mw-cite-backlink"><b><a href="#cite_ref-5">^</a></b></span> <span class="reference-text">Some resources related to the current version of <a rel="nofollow" class="external text" href="http://www.rm-odp.net/files/resources/LON-040_UML4ODP_IS/LON-040_UML4ODP_IS.pdf">| ITU-T X.906 | ISO/IEC 19793 "Use of UML for ODP systems specifications"</a> are also available from the <a rel="nofollow" class="external text" href="http://www.rm-odp.net">RM-ODP resource site</a>. They include the UML Profiles of the five ODP viewpoints, the viewpoint metamodels, the GIF files for the ODP-specific icons, etc.</span>

</li>

</li>

</li>

</li>

</li>

<li id="cite_note-10"><span class="mw-cite-backlink"><b><a href="#cite_ref-10">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://www.opengroup.org/combine/overview.htm">COMBINE</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20080515223146/http://www.opengroup.org/combine/overview.htm">Archived</a> 2008-05-15 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a></span>

</li>

<li id="cite_note-11"><span class="mw-cite-backlink"><b><a href="#cite_ref-11">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://envri.eu/rm">ENVRI Reference Model</a></span>

</li>

<li id="cite_note-12"><span class="mw-cite-backlink"><b><a href="#cite_ref-12">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://public.ccsds.org/review/default.aspx">Reference Architecture for Space Data Systems (RASDS)</a></span>

</li>

<li id="cite_note-13"><span class="mw-cite-backlink"><b><a href="#cite_ref-13">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://www.net.intap.or.jp/e">Interoperability Technology Association for Information Processing (INTAP)</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20080311015257/http://www.net.intap.or.jp/e/">Archived</a> 2008-03-11 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a></span>

</li>

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><cite id="CITEREFO'MooreDe_MoorBoranGaffney1994" class="citation journal cs1">O'Moore, R.R.; De Moor, G.; Boran, G.; Gaffney, P.; Grimson, J.; McNair, P.; Groth, T.; Nykänen, P.; Hasman, A.; Eller, J.; Yearworth, M. (1994). "OpenLabs: the application of advanced informatics and telematics for optimization of clinical laboratory services". <i>Computer Methods and Programs in Biomedicine</i>. <b>45</b> (<span class="nowrap">1–</span>2): <span class="nowrap">137–</span>140. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1016%2F0169-2607%2894%2990034-5">10.1016/0169-2607(94)90034-5</a>. <a href="PMID_(identifier)" class="mw-redirect" title="PMID (identifier)">PMID</a> <a rel="nofollow" class="external text" href="https://pubmed.ncbi.nlm.nih.gov/7889746">7889746</a>.</cite></span>

</li>

<li id="cite_note-15"><span class="mw-cite-backlink"><b><a href="#cite_ref-15">^</a></b></span> <span class="reference-text"><cite id="CITEREFGrimsonBrenderGrimsonGroth1996" class="citation journal cs1">Grimson, William; Brender, Jytte; Grimson, Jane; Groth, Torgny; Hermanson, Bo; Yearworth, Michael; Wade, Vincent (1996). "Specifying an open clinical laboratory information system". <i>Computer Methods and Programs in Biomedicine</i>. <b>50</b> (2): <span class="nowrap">95–</span>109. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1016%2F0169-2607%2896%2901739-R">10.1016/0169-2607(96)01739-R</a>. <a href="PMID_(identifier)" class="mw-redirect" title="PMID (identifier)">PMID</a> <a rel="nofollow" class="external text" href="https://pubmed.ncbi.nlm.nih.gov/8875017">8875017</a>.</cite></span>

</li>

<li id="cite_note-16"><span class="mw-cite-backlink"><b><a href="#cite_ref-16">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://www.cs.tcd.ie/synapses/public/">The Synapses Project: a three-year project funded under the EU 4th Framework Health Telematics Programme</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20050406000347/http://www.cs.tcd.ie/synapses/public/">Archived</a> 2005-04-06 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a></span>

</li>

<li id="cite_note-17"><span class="mw-cite-backlink"><b><a href="#cite_ref-17">^</a></b></span> <span class="reference-text">Kilov, H., Linington, P.F., Romero, J.R., Tanaka, A., Vallecillo, A.: The reference model of open distributed processing: foundations, experience and applications. Comput. Stand. Interfaces 35, 247–256 (2013)</span>

</li>

</ol></div></div>

<div class="mw-heading mw-heading2"><h2 id="External_links">External links</h2></div>

<ul><li><a rel="nofollow" class="external text" href="https://rm-odp-new.lcc.uma.es/">RM-ODP Resource site</a></li>

<li><a rel="nofollow" class="external text" href="http://www.joaquin.net/ODP/">Open Distributed Processing - Reference Model</a></li>

<li><a rel="nofollow" class="external text" href="http://lams.epfl.ch/reference/rm-odp">RM-ODP information at LAMS</a>, Swiss Federal Institute of Technology, Lausanne (EPFL), Switzerland.</li>

<li><a rel="nofollow" class="external text" href="http://www.ansa.co.uk/">Official Record of the ANSA project</a></li>

<li><a rel="nofollow" class="external text" href="http://www.cs.ukc.ac.uk/">Computing Laboratory</a>, University of Kent, Canterbury UK.</li>

<li><a rel="nofollow" class="external text" href="http://www.cs.stir.ac.uk/~kjt/research/formosa.html">FORMOSA</a> (Formalisation of ODP Systems Architecture), University of Stirling, UK.</li>

<li><a rel="nofollow" class="external text" href="http://www.lip6.fr/recherche/team.php?id=8&LANG=en">Distributed and Cooperative Systems</a>, UMPC, Paris, France.</li>

<li><a rel="nofollow" class="external text" href="http://www.infres.enst.fr/recherche/ILR/rapport.html">ILR</a>, Networks and ComputerScience Department of ENST, Paris France.</li>

<li><a rel="nofollow" class="external text" href="https://web.archive.org/web/20060103011745/http://archive.dstc.edu.au/AU/research_news/">Distributed Systems Technology Center</a>, Australia.</li>

<li><a rel="nofollow" class="external text" href="https://medium.com/@ianjoyner/open-distributed-processing-unplugged-bd3bde85f764">Open Distributed Processing: Unplugged!</a> a simple introduction by Ian Joyner.</li></ul></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2024-09-29" href="https://en.wikipedia.org/wiki/?title=RM-ODP&oldid=1248372750">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>